Node / acehoss / sortie.git rns://e35de29a61974cd952fde3fe9c8500d5/acehoss/sortie.git

🗀 Files • ☸ Work (0) • 🖹 Commits (1037) • ⑃ Branches (1) • ⌆ Tags (0) • ♥ Thanks (0)

T282828

Or via Homebrew: T383838brew install sortie-ai/tap/sortie

Coding agents can handle routine engineering tasks — bug fixes, dependency updates, test coverage, feature work — when they have good system prompts, appropriate tool permissions, and have been tested on representative issues. But running validated agents at scale requires infrastructure that doesn't exist yet: isolated workspaces, retry logic, state reconciliation, tracker integration, cost tracking. Teams build this ad-hoc, poorly, and differently each time.

Sortie is that infrastructure.

Define your T383838WORKFLOW.md in a single file alongside the target repository:

T282828

Sortie watches this file, polls for matching issues, creates an isolated workspace

for each, and launches the agent with the rendered prompt. It handles the rest:

stall detection, timeout enforcement, retries with backoff, state reconciliation

with the tracker, and workspace cleanup when issues reach terminal states. Changes

to the workflow are applied without restart.

The T383838agent.kind field selects which coding agent runs each session. Sortie ships

adapters for Claude Code, Copilot, and Codex — switching is a one-line change.

See the adapter reference for configuration

details and examples/ for complete workflow files.

Sortie is a single Go binary. It uses SQLite for persistent state (retry queues, session

metadata, run history) and communicates with coding agents over stdio. The orchestrator

is the single authority for all scheduling decisions; there is no external job queue or

distributed coordination. For full architectural details, see

docs/architecture.md.

Issue trackers and coding agents are integrated through adapter interfaces. Adding support

for a new tracker or agent is an additive change: implement the interface in a new package.

Supported trackers: GitHub Issues, Jira, and Linear. Supported agents: Claude Code, Copilot,

OpenCode, and Codex. See docs/decisions/ for detailed rationale on

technology choices.

Full configuration reference, CLI usage, and getting started guide:

Sortie's architecture is informed by OpenAI Symphony,

a spec-first orchestration framework with an Elixir reference implementation. Sortie diverges

in language (Go for deployment simplicity), persistence (SQLite instead of in-memory state),

extensibility (pluggable adapters for any tracker or agent, not hardcoded to Linear and Codex),

and completion signaling (orchestrator-managed handoff transitions instead of relying solely on

agent-initiated tracker writes).

A sortie is a military and aviation term for a single mission executed autonomously. The

metaphor is precise: the orchestrator dispatches agents on missions (issues), each with an

isolated workspace, a defined objective, and an expected return. The name is short, two

syllables, pronounceable across languages, and does not conflict with existing projects in

this domain.

See our project board for current status and priorities.